Reject

This operation transfers the relevant organisation's decision to reject the application from their IT system to the ePlanning.

path Parameters
CaseID
required
string

A fully qualified application number

header Parameters
OrganisationID
required
string

The relevant organisation name to indicate where the request is originated from.

IdempotencyID
required
string

Unique Id for this request. Allows the API to respond in an idempotent way if it has already been called with these parameters and prevents duplicate processing. Typically a UUID such as "63a9ba30-7a4b-4fac-b343-d1f05cf089f1"

Request Body schema: application/json
rejectDate
required
string <date>

This is to track the date of rejection

rejectReason
required
string

This is to track the different reasons for rejecting. One of the below mentioned values must be selected for reject reasons 1. The application is illegible or unclear as to the development consent sought 2. The application does not contain the information specified in Part 1 of Schedule 1 of the EP&A Regulation 3. The application is for State significant development or designated development and is not accompanied by an environmental impact statement

rejectReasonDescription
required
string <= 512 characters

This is to track the detailed reason the council is rejecting the application

updatedByEmail
string <= 250 characters

User must be registered in the planning portal

Responses

Request samples

Content type
application/json
{
  • "rejectDate": "2019-08-24",
  • "rejectReason": "Refer to description for values",
  • "rejectReasonDescription": "string",
  • "updatedByEmail": "john.smith@gmail.com"
}

Response samples

Content type
application/json
{
  • "statusCode": 404,
  • "message": "Internal Server error 19876",
  • "activityId": "00000011-0ab-xy00-0000-500000000000",
  • "errorCode": "DPE_TMS01",
  • "errorDetails": "Inner Exceptions, Stack Trace, etc"
}
Next to AllConsentConditions